Slice management system and slice management method

ABSTRACT

A slice management system and a slice management method that can dynamically adjust the amount of resources when the amount of resources is insufficient to create a slice. A storing unit of a NFVO stores slice utilization status information. In a BSS/OSS, an allocation determination unit determines to create a new slice or extend an existing slice, and when resources for creation of a new slice or extension of an existing slice are insufficient, a resource change determination unit determines a slice for reduction based on the slice utilization status information. A resource request unit of the NFVO reduces resources of the determined slice.

TECHNICAL FIELD

The present invention relates to a slice management system and a slicemanagement method.

BACKGROUND ART

A network system using existing virtualization technology virtuallydivides hardware resources to create slices, which are virtual networksthat are logically constructed on a network infrastructure, with use ofthe virtualization technology disclosed in Non Patent Literature 1. Thesystem then allocates a service to each of the slices and therebyprovides the service using a network in each of the slices that areisolated from one another. Thus, when allocating a slice to each ofservices having a variety of requirements, it is possible to easilysatisfy the requirement of each service and thereby reduce the signalingloads and the like.

CITATION LIST Non Patent Literature

NPL1: Akihiro Nakao, “Virtualization-node project: Virtualizationtechnology for new generation network”, [online], June 2010, NationalInstitute of Information and Communications Technology, [Searched onMar. 16, 2015], Internet<http://www.nict.go.jp/publication/NICT-News/1006/01.html>

SUMMARY OF INVENTION Technical Problem

However, there is a case where the amount of hardware resources to beallocated to a slice is insufficient, which causes a problem that aslice corresponding to a new service cannot be created, or, even when itis created, the operation of the system becomes unstable.

The present invention has been accomplished to solve the above problemsand an object of the present invention is thus to provide a slicemanagement system and a slice management method that can dynamicallyadjust the amount of resources in the case where the amount of resourcesis insufficient when creating a slice.

Solution to Problem

To achieve the above object, a slice management system according to oneembodiment of the present invention is a slice management system thatmanages a slice being a virtual network created on a networkinfrastructure, and the system includes a resource utilization statusinformation storage means configured to store information of autilization status of resources allocated to created slices, and aresource change means configured to specify a slice based on theinformation of the resource utilization status stored in the resourceutilization status information storage means in accordance withpredication information of the resource utilization status by creationof a new slice or extension of an existing slice, and reduce an amountof resources allocated to the slice.

A slice management method according to one embodiment of the presentinvention is a slice management method executed in a slice managementsystem that manages a slice being a virtual network created on a networkinfrastructure, and the method includes a resource change step ofspecifying a slice based on information of a utilization status ofresources allocated to created slices in accordance with predicationinformation of the resource utilization status by creation of a newslice or extension of an existing slice, and reducing an amount ofresources allocated to the slice.

According to the slice management system and the slice management methoddescribed above, because the amount of resources of an existing slice isreduced by using information of a utilization status of resourcesallocated to created slices in accordance with predication informationof the resource utilization status by creation of a new slice orextension of an existing slice, it is possible to dynamically adjust theamount of resources.

In the above-described slice management system, a slice may be specifiedwhen resources are found to be insufficient from the information of theresource utilization status and the predication information. Further, inthe resource change step, a slice may be specified when resources arefound to be insufficient from the information of the resourceutilization status and the predication information. In this case, evenwhen resources for creation of a new slice or extension of an existingslice are insufficient, it is possible to create a new slice or extendan existing slice by reducing the amount of resources of an existingslice.

Further, in the above-described slice management system, the resourcechange means may specify the slice where resources are to be reducedwhen resources for creation of a new slice or extension of an existingslice are found to be insufficient as a result of responding to arequest for allocating a slice to a service using the virtual network.Further, in the resource change step, the slice where resources are tobe reduced may be specified when resources for creation of a new sliceor extension of an existing slice are found to be insufficient as aresult of responding to a request for allocating a slice to a serviceusing the virtual network. In this case, because the slice managementsystem carries out the reduction of resources to be allocated to a sliceat the time of receiving a service request, it is possible todynamically adjust the amount of resources so that the slice can beallocated to the service.

Advantageous Effects of Invention

According to one embodiment of the present invention, it is possible todynamically adjust the amount of resources so that a slice can beallocated to a service.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a view showing the configuration of a system according to anembodiment of the present invention.

FIG. 2 is a view showing the correspondence between slices andresources.

FIG. 3 is a block diagram of devices included in a system according toan embodiment of the present invention.

FIG. 4 is a view showing a slice management table.

FIG. 5 is a view showing a hardware utilization status table.

FIG. 6 is a view showing a slice utilization status table.

FIG. 7 is a view showing a service management table.

FIG. 8 is a view showing a service correspondence slice table.

FIG. 9 is a view showing a hardware table.

FIG. 10 is a hardware configuration diagram of BSS/OSS and the like.

FIG. 11 is a sequence chart according to an embodiment of the presentinvention.

DESCRIPTION OF EMBODIMENTS

Embodiments of a slice management system and a slice management methodaccording to the present invention are described hereinafter withreference to the drawings. Note that, in the description of thedrawings, the same elements are denoted by the same reference symbolsand redundant description thereof is omitted.

FIG. 1 shows the configuration of a system 1 (slice management system)that includes a BSS/OSS 10 and an NFVO 30 according to this embodiment.The system 1 is a system that allocates a service to a slice, which is avirtual network. The slice is a virtual network or service network thatis logically created on a network infrastructure by virtually dividinglink and node resources of a network device and coupling the dividedresources, and resources in the slices are isolated from one another anddo not interfere with one another. The service is a service usingnetwork resources such as a communication service (a leased line serviceetc.) and an application service (a video distribution service, aservice using a sensor device such as an embedded device etc.).

As shown in FIG. 1, the system 1 is composed of BSS/OSS (OperationsSupport System/Business Support System) 10, SO (Service Operator) 20,NFVO30, VNFM40, and VIM (Virtualized Infrastructure Management) 50.Further, the system 1 is composed of NFVI (NFV (Network FunctionsVirtualisation) Infrastructure) 60, SB SA (Service-Based SliceAllocator) 70, base station 80, and SU (Service User) 90. The NFVO 30,the VNFM 40 and the VIM 50 are MANO (Management & Orchestration)architecture.

Those elements constitute a core network of the system 1. Note that theelements that need to transmit and receive information to and from eachother are connected by wired connections or the like so that they cantransmit and receive information.

The system 1 according to this embodiment provides a communicationfunction to a mobile communication terminal by a virtual server thatoperates in a virtual machine which is implemented on a physical server.Specifically, the system 1 is a virtualized mobile communicationnetwork. The communication function is provided to the mobilecommunication terminal by executing communication processingcorresponding to the communication function by the virtual machine.

The NFVI 60 is a network that is formed by physical resources (a groupof nodes) that constitute a virtualized environment. Conceptually, thephysical resources include computational resources, storage resourcesand transmission resources. The physical resources are composed of nodessuch as a physical server, which is a physical server device thatperforms communication processing in the system 1, and switches. Thephysical server is composed of a CPU (core, processor), a memory, and astorage means such as a hard disk. Generally, nodes such as physicalservers that constitute the NFVI 60 are collectively located in a pointsuch as a data center (DC). In the data center, the physical serverslocated therein are connected by a network in the data sensor, so thatthey can transmit and receive information to and from each other.Further, there are a plurality of data centers in the system 1. The datacenters are connected by a network, and physical servers located indifferent data centers can transmit and receive information to and fromeach other through the network.

The SO (Service Operator) 20 is a device that requests a service, and itis, for example, a terminal device (e.g., personal computer etc.) of abusiness operator that provides services to various users with use ofvirtual networks.

The BSS/OSS 10 is a node that performs service management in the system1 and gives instructions related to the communication function in thesystem 1. For example, the BSS/OSS 10 gives an instruction to add a newcommunication function (communication service) to the NFVO 30. Further,the BSS/OSS 10 can be operated by a telecommunications carrier relatedto the system 1.

The NFVO 30 is an overall management node (functional entity) thatperforms management of all virtual networks (slices) constructed on theNFVI 60, which is a physical resource. The NFVO 30 receives aninstruction from the BSS/OSS 10 and performs processing in accordancewith the instruction. The NFVO 30 performs management of all virtualizednetworks constructed in the physical resources of the mobilecommunication network of the infrastructure and communication service.The NFVO 30 implements the communication service that is provided by avirtual network in an appropriate place via the VNFM 40 and the VIM 50.For example, service life cycle management (specifically, creation,update, scale control, event collection, etc.), resource distribution,reservation and allocation management in the entire mobile communicationnetwork, service instance management, and policy management(specifically, optimal placement based on resource reservation,allocation, geography, laws and regulations etc.)

The VNFM 40 is a virtual communication function management node(functional entity) that adds a function related to a service to theNFVI 60, which is a physical resource (node). A plurality of VNFMs 40may be placed in the system 1.

The VIM 50 is a physical resource management node (functional entity)that manages each of physical resources (nodes) in the NFVI 60.Specifically, it performs management of resource allocation, update andcollection, association of a physical resource with a virtualizednetwork, and management of a list of hardware resources and SW resources(hypervisor). Generally, the VIM 50 performs management for each datacenter (exchange). The management of physical resources is performed bya scheme corresponding to the data center. There are several types ofmanagement schemes of the data center (implementation schemes ofmanagement resources) such as OPENSTACK and vCenter. In general, the VIM50 is placed for each data center management scheme. Specifically, aplurality of VIMs 50 that respectively manage the physical resources inthe NFVI 60 by different schemes from one another arc included. Notethat the physical resources are not necessarily managed by differentschemes for each data center.

Note that the NFVO 30, the VNFM 40 and the VIM 50 are implemented byexecuting a program on a physical server device (note that, however, theway of implementation on virtualization is not particularly limited, anda management system may be separated and implemented on virtualization).The NFVO 30, the VNFM 40 and the VIM 50 may be implemented by separatephysical server devices or may be implemented by the same server device.The NFVO 30, the VNFM 40 and the VIM 50 (i.e. programs for implementingthem) may be provided from different vendors.

The NFVO 30 receives a service allocation request from the BSS/OSS 10and then makes a resource reservation request for slices (slices SL1,SL2 etc.) to the VIM 50. When the VIM 50 reserves resources in a serverdevice and switches that form the NFVIs 60, the NFVO 30 defines slicesfor those NFVIs 60.

Further, after the NFVO 30 causes the VIM 50 to reserve resources in theNFVI 60, it stores information that defines a slice for the NFVI 60 intoa table stored in the NFVO 30. Then, the NFVO 30 makes a request toinstall software for implementing a function required for the service tothe VNFM 40. In response to the installation request, the VNFM 40installs the software into the NFVI 60 (a node such as a server device,a switch device or a router device) that has been reserved by the VIM50.

When the software is installed by the VNFM 40, the NFVO 30 associatesthe slice and the service into the table stored in the NFVO 30.

For example, as shown in FIG. 2, when the NFVO 30 makes a resourcereservation request for slices (slice 1 and slice 2) to the VIM 50, theVIM 50 gives an instruction indicating that request to a switch SW1, aswitch SW2, a server SV1 and a switch SW3. Then, the switch SW1, theswitch SW2, the server SV1 and the switch SW3 reserve resources for theslice 1. Likewise, in accordance with an instruction from the VIM 50,the switch SW1, the switch SW2, the server SV1 and a switch SW4 reserveresources for the slice 2.

Further, when resources arc reserved in switches or the like, the NFVO30 allocates the service 1 to the slice 1, and allocates the service 2to the slice 2. In this manner, the NFVO 30 allocates services to theslices that are isolated from one another. Note that a plurality ofservices may be allocated to each slice.

After the NFVO 30 allocates a service to a slice, it transmits accessinformation that contains the ID of this service and the address (e.g.,IP address) of hardware that provides the first function of this serviceto the BSS/OSS 10.

When the BSS/OSS 10 receives the access information, it notifies eachSBSA 70 of the access information. The SBSA 70 is a server device thatcan communicate with the base station 80, and when a service request ismade, with a service ID, from the SU (Service User) 90 to the basestation 80, the base station 80 notifies the SBSA 70 of the service IDreceived from the SU 90.

When the SBSA 70 receives the service ID from the base station 80, ittransmits, to the base station 80, the address information of thehardware that provides the first function of the service of the accessinformation corresponding to the service ID received from the basestation 80. The base station 80 notifies the SU 90 of this addressinformation. The SU 90 can thereby specify the address to be accessedfirst to use the service.

Hereinafter, the functions related to this embodiment of the BSS/OSS 10,the NFVO 30, the VNFM 40 and the VIM 50 are described with reference toFIG. 3. As shown in FIG. 3, the BSS/OSS 10 includes a service requestreceiving unit 11, an information receiving unit 12, an allocationdetermination unit 13 a resource change determination unit 14 (resourcechange means), a resource change request unit 15, an allocation requestunit 16, and an allocation result notification unit 17.

The service request receiving unit 11 is a part that receives a servicerequest containing service requirements, which are requirements for thefunction or performance in the service from the SO. Among the servicerequirements, the functional requirements are requirements related tothe function for carrying out the service. To be specific, thefunctional requirements include the necessity of mobility control, apossible access area range and a service use time. The necessity ofmobility control means whether handover control is required or not. Theaccess area range means the range (area) where a service is provided.

The service use time means a period of time when a service is used.

The performance requirements are requirements related to the performanceof the slice for carrying out the service. To be specific, theperformance requirements include an allowed lower limit bandwidth, anallowed delay time, a minimum packet loss rate and the like. The allowedlower limit bandwidth indicates the lower limit of the frequency band tobe used for communication, the allowed delay time means the length oftime a communication delay is allowed, and the minimum packet loss rateindicates an allowable packet loss rate.

Further, at the time of receiving a service request, the service requestreceiving unit 11 receives information indicating the function forimplementing the service. The information indicating the function forimplementing the service includes information for specifying thefunction (function identifying information, function name etc.).Further, the service request receiving unit 11 may receive software forimplementing the function from the SO 20.

When the service request receiving unit 11 receives the above-describedservice requirements and information indicating the function forimplementing the service, it transmits the service requirements to theallocation determination unit 13, and transmits the informationindicating the function for implementing the service (functionalinformation) to the allocation request unit 16. Further, at this timing,the service request receiving unit 11 notifies the information receivingunit 12 that the service request has been received. The functionalinformation contains information for identifying a function and softwarefor implementing the function.

The information receiving unit 12 receives information about slices fromthe NFVO 30 and acquires information about the utilization status ofresources allocated to created slices. To be specific, when theinformation receiving unit 12 receives a notification about the receiptof a service request from the service request receiving unit 11, itsends a request for transmitting slice attribute information, hardwareutilization status information, and slice utilization status informationto the NFVO 30.

Note that the NFVO 30 stores information of a slice management tablecontaining slice attribute information, a hardware utilization statustable containing hardware utilization status information, and a sliceutilization status table containing slice utilization statusinformation. When the NFVO 30 receives the information transmissionrequest from the information receiving unit 12, it transmits informationof the slice management table, information of the hardware utilizationstatus table and information of the slice utilization status table tothe BSS/OSS 10.

FIG. 4 shows an example of the slice management table stored in the NFVO30. The slice management table has a slice ID, an available node, thecapability of mobility control, a possible access area range, a serviceuse time, an available bandwidth, a minimum delay time, a minimum packetloss rate, a resource utilization rate, and a flag for availability ofreceipt of multiple services.

The slice ID is an ID for uniquely identifying a record that isdetermined when the NFVO 30 adds a new record to the slice managementtable. The available node indicates a node that is reserved by the VIM50 (a node that constitutes the NFVI 60) as a result of making aresource reservation request to the VIM 50. Information defined by theavailable node includes information that identifies a node (hardwarename etc.) and the amount of resources allocated in each node (a memoryoccupancy, a CPU occupancy rate etc.). The capability of mobilitycontrol is information indicating whether the available node is capableof mobility control or not. The possible access area range isinformation indicating an accessible area based on the location of theavailable node. The service use time is information indicating a timewhen a service is available based on the available node. The availablebandwidth is information indicating the maximum bandwidth that can beprovided in the available node.

The minimum delay time indicates the minimum delay time based on theavailable node. The minimum packet loss rate indicates the minimumpacket loss rate based on the available resources. The resourceutilization rate indicates the utilization rate of resources allocatedin the current node. The flag for availability of receipt of multipleservices is a value indicating whether a service that is designated tobe isolated from another service is allocated or not, and when a servicethat is designated to be isolated from another service is allocated,information indicating that (e.g., “1”) is set.

FIG. 5 shows an example of the hardware utilization status table. Thehardware utilization status table has an HW name, a slice being used,allocated resources, a resource utilization rate, and excess resources.The HW name is a hardware name that can uniquely identifies a serverdevice or a switch. The slice being used is information (e.g., slide ID)of the slice to which the device is allocated. The allocated resourcesare the amount of resources allocated to each slice, which are resourcesto be used for the existing slices. The resource utilization rate is theutilization rate of resources in each slice. The excess resources meansresources that are not allocated to any slice, which correspond to anunallocated CPU core and clock frequency, an unallocated memory region,an unallocated storage capacity, and an unallocated queue.

FIG. 6 shows an example of the slice utilization status table. The sliceutilization status table has a slice ID, a hardware ID, resources, amemory utilization rate, a CPU utilization rate, a storage utilizationrate, and a bandwidth utilization rate. The slice ID is the ID of eachslice. The hardware ID is the ID assigned to each hardware. Theresources are the amount of resources allocated to each slice. Thememory utilization rate is a utilization rate related to a memory ofeach allocated hardware. To be specific, the memory utilization ratemeans the ratio of a memory region that is used in a slice to theallocated memory region. The CPU utilization rate is a utilization raterelated to a CPU of each allocated hardware. To be specific, the CPUutilization rate is the ratio of a CPU core and a clock frequency usedin a slice to the allocated CPU core and clock frequency. The storageutilization rate is a utilization rate related to a storage of eachallocated hardware. To be specific, the storage utilization rate meansthe ratio of a storage region that is used in a slice to the allocatedstorage region. The bandwidth utilization rate is a utilization raterelated to a bandwidth of each allocated hardware. To be specific, thebandwidth utilization rate means a bit rate used in a slice to themaximum output bit rate of an allocated queue or a virtual MC. Thebandwidth utilization rate in a server indicates the bandwidthutilization rate of a virtual MC.

The information receiving unit 12 receives information contained in theslice management table from the NFVO 30 and then transmits theinformation to the allocation determination unit 13. Using thisinformation, the allocation determination unit 13 determines whether toallocate the requested service to an existing slice or to a new slice.The information receiving unit 12 receives the slice utilization statusinformation and the hardware utilization status information and thentransmits those information to the resource change determination unit14. Using the hardware utilization status information, the resourcechange determination unit 14 determines whether it is possible to newlycreate a slice or extend an existing slice. When there are no sufficientresources to newly create a slice or extend an existing slice, theresource change determination unit 14 determines a slice where resourcesare to be reduced based on the slice utilization status information andthe slice utilization status information.

The allocation determination unit 13 is a part that determines to whichof an existing slice and a new slice the service is to be allocatedbased on the service requirements of the service received by the servicerequest receiving unit 11 and the attribute of the existing slice. Theallocation determination unit 13 receives the service requirements fromthe service request receiving unit 11 and receives the slice informationfrom the information receiving unit 12 and, using the servicerequirements and the slice information, determines to which of anexisting slice and a new slice the service is to be allocated.

First, in the case where the service requirements include a requirementindicating isolation from another service (isolation requirement), theallocation determination unit 13 determines to allocate the service to anew slice. On the other hand, in the case where the service requirementsdo not include a requirement indicating isolation from another service,the allocation determination unit 13 determines whether the attributeinformation of an existing slice that satisfies the service requirementsexists or not.

In the case where the attribute information of an existing slice thatsatisfies the service requirements exists, the allocation determinationunit 13 determines to allocate (accommodate) the requested service tothis existing slice, and transmits this determination result to theallocation request unit 16.

Further, there is a case where it is determined that addition to acurrent slice is not possible even when the functional and performancerequirements are satisfied based on the utilization rate of an availablenode. In such a case, the allocation determination unit 13 determines toextend an existing slice or add a new slice. In this case, theallocation determination unit 13 notifies the resource changedetermination unit 14 of this determination, and receives adetermination result as to whether it is possible to extend an existingslice or add a new slice from the resource change determination unit 14.

For example, in the case where there is a slice that satisfies thefunctional and performance requirements other than the utilization rateof an available node, the allocation determination unit 13 determines toallocate the service to this slice, and notifies the resource changedetermination unit 14 of the amount of resources required for theextension (e.g., the amount of resources to be cut) and the slice to beextended.

On the other hand, in the case where there is no slice that satisfiesthe functional and performance requirements other than the utilizationrate of an available node, the allocation determination unit 13determines to create a new slice and allocate the service to this slice,and notifies the resource change determination unit 14 of creation of anew slice and the amount of resources required for the service.

When the allocation determination unit 13 determines to extend anexisting slice or add a new slice and receives a notification that it ispossible to extend an existing slice or add a new slice from theresource change determination unit 14, it sends a notification ofextending an existing slice or adding a new slice to the allocationrequest unit 16.

After the allocation determination unit 13 determines whether to createa new slice and allocate the service, allocate the service to anexisting slice, or extend an existing slice and allocate the service, itsends the result of determination to the allocation request unit 16.

In the case where the allocation determination unit 13 determines tocreate a new slice and allocate the service, it sends, as the result ofdetermination, a notification of generating a new slice and the servicerequirements to the allocation request unit 16.

In the case where the allocation determination unit 13 determines toallocate the service to an existing slice, it sends, as the result ofdetermination, a notification of allocating the service to an existingslice, the slice ID of the existing slice, and the service requirementsto the allocation request unit 16.

In the case where the allocation determination unit 13 determines toextend an existing slice and allocate the service, it sends, as theresult of determination, a notification of extending an existing sliceand allocating the service, the slice ID of the existing slice, theamount of resources to be extended, and the service requirements to theallocation request unit 16.

The resource change determination unit 14 is a part that determineswhether it is possible to create a new slice or extend an existing sliceor not. Further, the resource change determination unit 14 is a partthat, when resources are found to be insufficient as a result of tryingto create a new slice or extend an existing slice, performsdetermination processing that determines a slice where the amount ofallocated resources is to be reduced based on information of theresource utilization status. Specifically, the resource changedetermination unit 14 specifies a slice based on information of theresource utilization status (e.g., resource utilization rate) accordingto predication information of the resource utilization status bycreation of a new slice or extension of an existing slice. Note that thepredication information of the resource utilization status isinformation based on a change in the resource utilization status, and itcorresponds to the amount of resources required for creation of a newslice or extension of an existing slice, a difference value between theamount of resources required for creation of a new slice or extension ofan existing slice and the excess resources, for example.

The resource change determination unit 14 receives the slice utilizationstatus information and the hardware utilization status information fromthe information receiving unit 12 and, using those information,determines whether it is necessary to change resources or specifies aslice where resources are to be changed.

When the resource change determination unit 14 receives a notificationof creating a new slice and the amount of resources required for theservice from the allocation determination unit 13, it refers to theexcess resources in the hardware utilization status information anddetermines whether there is an amount of resources required for theservice, and when there is an amount of resources required for theservice, it notifies the allocation determination unit 13 that it ispossible to create a new slice.

On the other hand, when the resource change determination unit 14determines that there is no amount of resources required for theservice, it refers to the slice utilization status table and determinesa slice where at least one utilization rate of the memory utilizationrate, the CPU utilization rate, the storage utilization rate and thebandwidth utilization rate is lower than a prestored threshold (e.g.,the utilization rate is 20% or less) as a target slice for reduction.Note that the resource change determination unit 14 may determine atarget slice for reduction by comparing the highest utilization rateamong the plurality of types of utilization rates described above withthe threshold, or may determine a target slice for reduction bycomparing the average of all of the plurality of types of utilizationrates described above with the threshold. The resource changedetermination unit 14 notifies the resource change request unit 15 ofthe target slice for reduction and the amount of resources to bereduced. When the resource change determination unit 14 receives anotification of completion of resource change from the resource changerequest unit 15, it notifies the allocation determination unit 13 thatit is possible to create a new slice.

When the resource change determination unit 14 receives a notificationof extending an existing slice and the amount of resources required forthe extension from the allocation determination unit 13, it refers tothe excess resources in the hardware utilization status information ofthe existing slice to be extended and determines whether the extensionis possible or not, and in the case where the extension is possible,notifies the allocation determination unit 13 that it is possible toextend the existing slice.

On the other hand, in the case where there is no excess resources forextension in the existing slice to be extended, the resource changedetermination unit 14 refers to the slice utilization status table and,when there is hardware where at least one utilization rate of the memoryutilization rate, the CPU utilization rate, the storage utilization rateand the bandwidth utilization rate in the hardware allocated to theexisting slice to be extended is low (e.g., the utilization rate is 20%or less), determines this existing slice to be extended as a targetslice for reduction. The resource change determination unit 14 notifiesthe resource change request unit 15 of the target slice for reductionand the amount of resources to be reduced. When the resource changedetermination unit 14 receives a notification of completion of resourcechange from the resource change request unit 15, it notifies theallocation determination unit 13 that it is possible to extend theexisting slice.

The resource change request unit 15 is a part that makes a resourcechange request to the NFVO 30 based on a notification from the resourcechange determination unit 14. When the resource change request unit 15receives the target slice for reduction and the amount of resources tobe reduced from the resource change determination unit 14, it notifiesthe NFVO of the target slice for reduction and the amount of resourcesto be reduced and makes a resource change request. In response to theresource change request, the NFVO 30 changes resources and then sends anotification of completion of resource change to the BSS/OSS 10. Theresource change request unit 15 receives the notification of completionof resource change and sends a notification of completion of resourcechange to the resource change determination unit 14.

The allocation request unit 16 is a part that makes a request forallocating the service to the slice determined by the allocationdetermination unit 13. To be specific, the allocation request unit 16transmits a result of determination by the allocation determination unit13 described above from the allocation determination unit 13 to the NFVO30 and makes a service allocation request. Then, the NFVO 30 allocatesthe service to the slice.

The allocation result notification unit 17 is a part that receives aresult of allocation from the NFVO 30. To be specific, the allocationresult notification unit 17 receives a result of allocation (a resultindicating whether allocation is completed or allocation cannot be done)from the NFVO 30. The information indicating completion of allocationcontains the service ID and the address of an access destination. In thecase where the allocation result is completion of allocation, theallocation result notification unit 17 transmits the service ID and theaccess destination to the SBSA 70.

The NFVO 30 includes an information transmitting unit 31, a resourcechange receiving unit 32, a service allocation request receiving unit33, a storing unit 34 (resource utilization status information storagemeans), a resource request unit 35 (resource change means), a functionaddition request unit 36, and a service allocation unit 37. Theinformation transmitting unit 31 receives an information transmissionrequest from the BSS/OSS 10 and then transmits information of the slicemanagement table, information of the slice utilization status table andinformation of the hardware utilization status table to the BSS/OSS 10.

The resource change receiving unit 32 is a part that receives, from theBSS/OSS 10, the target slice for reduction and the amount of resourcesto be reduced, and a resource change request. When the resource changereceiving unit 32 receives the resource change request, it notifies theresource request unit 35 of the target slice for reduction and theamount of resources to be reduced and causes it to change resources. Theresource change receiving unit 32 receives a notification of resourcechange from the resource request unit 35, and then gives a notificationof resource change to the BSS/OSS 10.

The service allocation request receiving unit 33 is a part thatreceives, from the BSS/OSS 10, a result of determination by theallocation determination unit 13 and a service allocation request. Inthe case where the result of determination by the allocationdetermination unit 13 includes “extending an existing slice andallocating the service” or “generating a new slice”, the serviceallocation request receiving unit 33 sends information about resourcesto the resource request unit 35.

Further, when the service allocation request receiving unit 33 receivesa notification of resource reservation from the resource request unit35, it gives a notification of the reservation to the BSS/OSS 10.Further, the service allocation request receiving unit 33 receivesfunctional information at specified timing. When the service allocationrequest receiving unit 33 receives the functional information, it sendsthe functional information to the function addition request unit 36.

After the service allocation unit 37 allocates the service, the serviceallocation request receiving unit 33 receives a result of allocationfrom the service allocation unit 37 and transmits the result ofallocation to the BSS/OSS 10.

The storing unit 34 is a part that stores various types of tables. Thestoring unit 34 stores the slice management table, the slice utilizationstatus table, the hardware utilization status table, the servicemanagement table, and the service correspondence slice management table.FIG. 7 shows the service management table. The service management tableis information based on the service requirements which the serviceallocation request receiving unit 33 has received from the BSS/OSS 10.The service management table has a service ID, mobility control, anaccess area range, a service use time, an allowed lower limit bandwidth,an allowed delay time, an allowed packet loss, a function, and anisolation flag. The service allocation unit 37 registers informationwhere a service ID is added to the service requirements in the servicemanagement table.

FIG. 8 shows the service correspondence slice management table. Theservice correspondence slice management table has a service ID and aslice ID. The service allocation unit 37 registers a service ID wheninformation is added to the service management table and a slice IDwhere the service is to be allocated in the service correspondence slicemanagement table.

The resource request unit 35 is a part that makes a request for resourcereservation to the VIM 50. The resource request unit 35 requests the VIM50 to reserve resources corresponding to the amount of resourcesreceived from the service allocation request receiving unit 33. When theresource request unit 35 receives a notification of completion ofresource reservation from the VIM 50, it gives the notification to theservice allocation request receiving unit 33.

The function addition request unit 36 is a part that makes a request forfunction addition to the VNFM 40. The function addition request unit 36requests the VNFM 40 to reserve resources corresponding to the amount ofresources received from the service allocation request receiving unit33. When the function addition request unit 36 receives a notificationof completion of function addition from the VNFM 40, it gives thenotification to the service allocation unit 37.

The service allocation unit 37 is a part that allocates the service.When a notification of completion of function addition is received bythe function addition request unit 36, the service allocation unit 37registers information based on the service requirements in the servicemanagement table and further registers a service ID and a slice ID inthe service correspondence slice management table.

The VNFM 40 is described hereinafter. The VNFM 40 includes a functionaddition request receiving unit 41, a storing unit 42, and a functionaddition unit 43. The function addition request receiving unit 41 is apart that receives a function addition request from the NFVO 30. Thefunction addition request receiving unit 41 notifies the functionaddition unit 43 that it has received a function addition request.Further, when the function addition request receiving unit 41 receivessoftware related to an additional function from the NFVO 30, it sendsthis software also to the function addition unit 43.

When the function addition request receiving unit 41 receives anotification of completion of function addition after addition of afunction by the function addition unit 43, it gives a notification ofcompletion of function addition to the NFVO 30.

The storing unit 34 is a part (e.g., repository) that stores software.The storing unit 34 stores software related to communication which islikely to be used in common.

The function addition unit 43 is a part that installs a function. Whenthe function addition unit 43 receives a function addition request fromthe function addition request receiving unit 41, it carries outinstallation to the target available node. At the time of installation,when the requested function is the function of software stored in thestoring unit 42, the function addition unit 43 installs the softwarestored in the storing unit 42 to the available node. When, on the otherhand, the function addition unit 43 receives software to be installedfrom the function addition request receiving unit 41, it installs thesoftware. After the installation is completed, the function additionunit 43 gives a notification of completion of installation to the NFVO30.

The VIM 50 includes a resource request receiving unit 51, a storing unit52, a resource reservation unit 53, and a monitoring unit 54. Theresource request receiving unit 51 is a part that receives a resourcereservation request from the NFVO 30. When a resource request isreceived, the request is notified to the resource reservation unit 53.The storing unit 52 is a part that stores information about resources.The storing unit 52 stores information of a hardware table.

When the VIM 50 receives a request for transmitting hardware informationand identification information of an available node from the BSS/OSS 10,it acquires the hardware information corresponding to the identificationinformation of the available node from the hardware table.

FIG. 9 shows the hardware table stored in the VIM 50. The hardware tableis a table that manages hardware information containing an HW name, theamount of resources, and the amount of electricity.

The HW name is identification information of hardware. The amount ofresources indicates the amount of resources of the hardware such as amemory capacity and CPU capabilities (number, execution speed etc.). Theamount of electricity is the amount of electricity when the entirehardware is used.

The VIM 50 receives the hardware information corresponding to theidentification information of the available node from the hardware tableand then transmits the information to the BSS/OSS 10.

The resource reservation unit 53 is a part that reserves resources. Whena notification of a resource request is received by the resource requestreceiving unit 51, the resource reservation unit 53 allocates a slicebased on excess resources. After reserving the resources, the resourcereservation unit 53 gives a notification to the resource requestreceiving unit 51. The monitoring unit 54 is a part that monitors theutilization status of the NFVI 60. The monitoring unit 54 reflects aresult of monitoring on the resource utilization rate.

The functions related to this embodiment are described above. FIG. 10shows the hardware configuration of a server device that implements theBSS/OSS 10, the NFVO 30, the VNFM 40 and the VIM 50. As shown in FIG.10, the server device is configured to include a computer that hashardware such as one or a plurality of CPU 101, RAM (Random AccessMemory) 102 and ROM (Read Only Memory) 103 serving as a main memorydevice, a communication module 104 (transmitter or receiver) forcommunication, and an auxiliary storage device 105 (memory) such as ahard disk. Those elements operate by a program or the like, and therebythe functions of the BSS/OSS 10, the NFVO 30, the VNFM 40 and the VIM 50described above are implemented.

Note that, instead of executing the functions in FIG. 3 by a processorsuch as the CPU 101, all or some of the functions may be executed byconstructing a dedicated integrated circuit (IC). For example, theabove-described functions may be executed by constructing a dedicatedintegrated circuit for performing image processing and communicationcontrol.

Software may be called any of software, firmware, middleware, microcode,hardware description language or another name, and it should be shouldbe interpreted widely so as to mean an instruction, an instruction set,a code, a code segment, a program code, a program, a sub-program, asoftware module, an application, a software application, a softwarepackage, a routine, a sub-routine, an object, an executable file, athread of execution, a procedure, a function and the like.

Further, software, instructions and the like may be transmitted andreceived via a transmission medium. For example, when software istransmitted from a website, a server or another remote source usingwired technology such as a coaxial cable, an optical fiber cable, atwisted pair and a digital subscriber line (DSL) and/or wirelesstechnology such as infrared rays, radio and microwaves, those wiredtechnology and/or wireless technology are included in the definition ofthe transmission medium.

Note that the BSS/OSS 10, the NFVO 30, the VNFM 40 and the VIM 50 may beimplemented by a computer system that is composed of a plurality ofserver devices. Further, a node different from the above-described nodesincluded in the system 1 may be implemented by a server device havingthe above-described hardware configuration. Further, some or all of thefunctions of the base station 80 and the SU 90 (mobile communicationterminal) may be implemented using hardware such as ASIC (ApplicationSpecific Integrated Circuit), PLD (Programmable Logic Device) and FPGA(Field Programmable Gate Array). Further, the base station 80 and the SU90 may be implemented by a computer device that includes a processor(CPU), a communication interface for network connection, a memory and acomputer-readable storage medium storing a program. In other words, thebase station 80, the SU 90 and the like according to one embodiment ofthe present invention may function as a computer that performsprocessing related to the present invention.

The processor, the memory and the like are connected through a bus forcommunicating information. Further, the computer-readable recordingmedium is an appropriate storage medium such as a flexible disk, amagneto-optical disk (e.g., compact disk, a digital versatile disc, aBlu-ray (registered trademark) disc), a smartcard, a flash memory device(e.g., a card, a stick, a key drive), a ROM, an EPROM (ErasableProgrammable ROM), an EEPROM (Electrically Erasable Programmable ROM), aCD-ROM (Compact Disc-ROM), a RAM, a register, a removable disk, a harddisk, a floppy (registered trademark) disk, a magnetic strip, adatabase, a server and the like. Further, the program may be transmittedfrom a network through a telecommunications line. Further, the basestation 80 and the SU 90 may include an input device such as an inputkey and an output device such as a display.

The functional configurations of the base station 80 and the SU 90 maybe implemented by the above-described hardware, may be implemented by asoftware module executed by a processor, or may be implemented by acombination of them. The processor causes an operation system to operateand controls a user terminal as a whole. Further, the processor reads aprogram, a software module and data from a storage medium to a memoryand performs various processing according to them.

Note that the program may be a program that causes a computer to executethe operations described in the above-described embodiment. For example,a control unit of the mobile communication terminal may be implementedby a control program that is stored in the memory and operates on theprocessor, and another functional block may be implemented in the samemanner. The system 1 according to this embodiment has theabove-described configuration.

A management method, which is a process executed in the system 1according to this embodiment, is described hereinafter with reference tothe sequence chart of FIG. 11. In this example, a process in the casewhere the BSS/OSS 10 determines to create a new slice or extend anexisting slice and allocate a service when a service start request ismade from the SO 20 is described.

First, when the SO 20 makes a service start request, the service requestreceiving unit 11 of the BSS/OSS 10 receives the service start request(Step S1). Next, the information receiving unit 12 makes an informationtransmission request to the NFVO 30 (Step S2), and receives informationfrom the NFVO 30 (Step S3). Then, the allocation determination unit 13performs service allocation slice determination processing (Step S4).Based on this determination, the resource change determination unit 14determines whether it is necessary to change resources (Step S5). Whenit is necessary to change resources, the resource change request unit 15makes a resource change request to the NFVO 30 (Step S6). In response tothe resource change request, the NFVO 30 makes a resource change requestto the VIM 50 (Step S7). Receiving the resource change request, the VIM50 changes resources (Step S8) and gives a resource change completionnotification to the NFVO 30 (Step S9). The NFVO 30 receives the resourcechange completion notification and gives a resource change completionnotification to the BSS/OSS 10 (Step S10).

The resource change request unit 15 receives the resource changecompletion notification from the NFVO 30 and gives a notification ofresource change to the resource change determination unit 14 and, inresponse to this, the resource change determination unit 14 gives anotification that it is possible to create a new slice or extend anexisting slice to the allocation determination unit 13. In response tothis notification, the allocation determination unit 13 causes theallocation request unit 16 to make a service allocation request (StepS11).

In response to the service allocation request, the NFVO 30 creates aslice (Step S12).

The operations and effects of the system 1 according to this embodimentare described hereinafter. The storing unit 34 of the NFVO 30 stores theslice utilization status information. In the BSS/OSS 10, the allocationdetermination unit 13 determines to create a new slice or extend anexisting slice and, when resources for creation of a new slice orextension of an existing slice are insufficient, the resource changedetermination unit 14 determines a slice where resources are to bereduced based on the slice utilization status information. The resourcerequest unit 35 of the NFVO 30 reduces the resources of the determinedslice.

In this case, because the system 1 reduces the amount of resources of anexisting slice by using information of the utilization status ofresources allocated to created slices even when resources are found tobe insufficient as a result of trying to create a new slice or extend anexisting slice, it is possible to dynamically adjust the amount ofresources.

Further, when it is determined that resources for creation of a newslice or extension of an existing slice after receiving a servicerequest from the SO 20, the resource change determination unit 14determines resources to be reduced. In this case, because the system 1carries out the reduction of resources to be allocated to a slice at thetime of receiving a service request, it is possible to dynamicallyadjust the amount of resources so that the slice can be allocated to theservice.

Although the case where the resource change determination unit 14 of theBSS/OSS 10 determines a slice where resources are to be reduced isdescribed in the above embodiment, the NFVO 30 may make thisdetermination.

Although the case where resources in an existing slice are reducedtriggered by receiving a service request is described in the aboveembodiment, this may be done at specified timing. For example, whetherthere is a slice where resources can be reduced may be determined duringstable operation. Further, resources in another slice may be reduced inorder to create (extend) a slice to be used preferentially in the eventof a disaster.

Although the case where the resource change determination unit 14determines whether resources are sufficient or not based on thepredication information of the resource utilization status and reducesresources in a slice when resources are found to be insufficient isdescribed in the above embodiment, it may determine whether theprobability that resources will become insufficient is high or not basedon the predication information of the resource utilization status andreduce resources in a slice when it is determined that the probabilityof insufficient resources is high (e.g., when the amount of resourcesrequired to create a new slice is larger than a prestored thresholdetc.)

Note that the term “specifying” used in this specification includes avariety of operations. For example, “specifying” can includedetermining, determining, calculating, computing, processing, deriving,investigating, looking up (e.g., looking up in a table, a database oranother data structure), ascertaining and the like. Further,“specifying” can include resolving, selecting, choosing, establishing,comparing and the like.

Further, the description “based on” used in this specification does notmean “based only on” unless otherwise noted. In other words, thedescription “based on” means both of “based only on” and “based at leaston”.

As long as “including”, “comprising” and transformation of them are usedin the present specification or claims, those terms are intended to becomprehensive like the term “comprising”. Further, the term “or” used inthe present specification or claims is intended not to be exclusive OR.

The term “connected” or every transformation of this term means everydirect or indirect connection or coupling between two or more elements,and it includes the case where there are one or more intermediateelements between two elements that are “connected” to each other. Theconnection between elements may be physical connection, logicalconnection, or a combination of them. When used in this specification,it is considered that two elements are “connected” to each other byusing one or more electric wires, cables and/or printed electricconnections and, as several non-definitive and non-comprehensiveexamples, by using electromagnetic energy such as electromagnetic energyhaving a wavelength of a radio frequency region, a microwave region andan optical (both visible and invisible) region.

The mobile communication terminal can be also called, by those skilledin the art, a mobile station, a subscriber station, a mobile unit, asubscriber unit, a wireless unit, a remote unit, a mobile device, awireless device, a wireless communication device, a remote device, amobile subscriber station, an access terminal, a mobile terminal, awireless terminal, a remote terminal, a handset, a user agent, a mobileclient, a client or several other appropriate terms.

The procedure, the sequence, the flowchart and the like in eachaspect/embodiment described in this specification may be in a differentorder unless inconsistency arises. For example, for the method describedin this specification, elements of various steps are described in anexemplified order, and it is not limited to the specific order describedabove.

Each aspect/embodiment described in this specification may be usedalone, may be used in combination, or may be used by being switchedaccording to the execution. Further, a notification of specifiedinformation (e.g., a notification of “being X”) is not limited to bemade explicitly, and it may be made implicitly (e.g., a notification ofthe specified information is not made).

Although the present invention is described in detail in the foregoing,it is apparent to those skilled in the art that the present invention isnot restricted to the embodiment described in this specification. Thepresent invention can be implemented as a modified and changed formwithout deviating from the spirit and scope of the present inventiondefined by the appended claims. Accordingly, the description of thepresent specification is given merely by way of illustration and doesnot have any restrictive meaning to the present invention,

REFERENCE SIGNS LIST

1 . . . system, 10 . . . BSS/OSS, 11 . . . service request receivingunit, 12 . . . information receiving unit, 13 . . . allocationdetermination unit, 14 . . . resource change determination unit, 15 . .. resource change request unit, 16 . . . allocation request unit, 17 . .. allocation result notification unit, 20 . . . SO, 30 . . . NFVO, 31 .. . information transmitting unit, 32 . . . resource change receivingunit, 33 . . . service allocation request receiving unit, 34 . . .storing unit, 35 . . . resource request unit, 36 . . . function additionrequest unit, 37 . . . service allocation unit, 40 . . . VNFM, 41 . . .function addition request receiving unit, 42 . . . storing unit, 43 . .. function addition unit, 50 . . . VIM, 51 . . . resource requestreceiving unit, 52 . . . storing unit, 53 . . . resource reservationunit, 54 . . . monitoring unit, 60 . . . NFVI, 70 . . . SBSA, 80 . . .base station, 90 . . . SU, 101 . . . CPU, 102 . . . RAM, 103 . . . ROM,104 . . . communication module, 105 . . . auxiliary storage device

1. A slice management system that manages a slice being a virtualnetwork created on a network infrastructure, comprising circuitryconfigured to: store information of a utilization status of resourcesallocated to created slices; and specify a slice based on theinformation of the resource utilization status stored in accordance withpredication information of the resource utilization status by creationof a new slice or extension of an existing slice, and reduce an amountof resources allocated to the slice.
 2. The slice management systemaccording to claim 1, wherein a slice is specified when resources arefound to be insufficient from the information of the resourceutilization status and the predication information.
 3. The slicemanagement system according to claim 2, wherein the slice managementsystem specifies the slice where resources are to be reduced whenresources for creation of a new slice or extension of an existing sliceare found to be insufficient as a result of responding to a request forallocating a slice to a service using the virtual network.
 4. A slicemanagement method executed in a slice management system that manages aslice being a virtual network created on a network infrastructure,comprising: a resource change specifying a slice based on information ofa utilization status of resources allocated to created slices inaccordance with predication information of the resource utilizationstatus by creation of a new slice or extension of an existing slice, andreducing an amount of resources allocated to the slice.
 5. The slicemanagement method according to claim 4, wherein the resource changespecifies a slice when resources are found to be insufficient from theinformation of the resource utilization status and the predicationinformation.
 6. The slice management method according to claim 5,wherein the resource change specifies the slice where resources are tobe reduced when resources for creation of a new slice or extension of anexisting slice are found to be insufficient as a result of responding toa request for allocating a slice to a service using the virtual network.